Interactive electronic communications and control system

ABSTRACT

A system comprising a database containing user data, an interface engine that communicates with the database and parses the data, an application server that communicates with the interface engine, a user device that receives and displays the parsed data, receives user-provided information, and sends the user-provided information to the application server, wherein the application server automatically updates the user device display with the parsed data, receives user-provided information from said user device, and provides the user-provided information to the interface engine for updating the database.

PRIORITY CLAIM TO PROVISIONAL APPLICATIONS

This non-provisional application claims the benefit of and priority toU.S. Provisional Application No. 62/420,945, filed Nov. 11, 2016 and62/551,402 filed Aug. 29, 2017, which are each incorporated herein byreference in their entirety for all purposes under the law.

FIELD OF THE INVENTION

The subject matter disclosed herein generally relates to an interactiveelectronic communications and control system tailored for facilities inany number of industries. The disclosure focuses on the healthcareindustry, describing systems, devices and methods for the communication,control and interactive sharing of, for example, admission, medical,educational, diet, entertainment and other parsed data and contentrelating to a patient's medical condition, treatment and stay at ahealthcare institution. It will be understood that the invention is notlimited to applications in the healthcare industry but can also beapplied to other industries as well including industries where tailoredcontent is provided to specialized audiences, allowing for high-levelinteraction between those audiences and the system to advanceinstitutional and other objectives.

BACKGROUND OF THE INVENTION

As of 2016, there were over 5,000 registered hospitals, nearly 900,000staffed beds, and over 35,000,000 patient admissions in the UnitedStates alone. (Source: American Hospital Association 2017 Fast Factsthat can be found athttp://www.aha.org/research/rc/stat-studies/fast-facts.shtml).

Healthcare institutions (e.g., hospitals, multiple facility healthcaresystems, and other single or multiple facility healthcare institutions)have historically focused on improving the quality of care, efficiencyof care, and quality of stay for their patients. Patient-related data,such as patient medications, lab results, physician assignments, roomassignments, and other key information have been used in one way or theother to attempt to help satisfy these objectives.

Over the years, serious challenges arose, and still exist today,relating to the utilization of such information. For example, patientinformation, especially in today's high-tech healthcare environment, canbe very complex, and major compatibility issues often exist between thevariety of hardware and software systems that institutions utilize instoring and managing such information.

Furthermore, as institutions utilize more information from outside ofthe institutions themselves, a greater amount of resources have goneinto devising systems that seek to access information from a significantnumber of external disparate sources. Systems configured to attempt toaddress these complex issues have required numerous customizedcomponents (e.g., local and remote physical servers) organized in acomplex manners giving rise to significant installment and maintenancecosts, inefficiencies and technical problems.

As described herein, the present invention resolves these and otherproblems by providing systems, devices and methods generally locally atthe institution site utilizing virtual machine servers combined withappropriate novel integration and application programs. This approach,as described herein, enhances the delivery of information within ahealthcare institution in many respects, including allowing the systemto operate within many diverse host environments and datacenters toprovide, for example, enhanced disaster recovery, uptime andscalability.

This approach also eliminates the need to rely on third party videostreaming vendors, the need to supply hardware on site, and provides aspecialized information system unique to the healthcare industry,eliminating the need to adapt applications built to serve datacenterinfrastructure of other industries, such as the hotel industry. Thisapproach is also beneficial because the system does not have to relyupon and draw from disparate hardware and software sources and thirdparty proprietary equipment to function in the manner as describedherein.

In other aspects, institutions and other organizations utilize localizedmedia and communications systems to communicate and interact withspecific audiences by, among other things, providing specialized mediacontent and services to those audiences. For example, healthcareinstitutions utilize such systems to present specialized media contentto inpatients relating to their care, and to allow patients to each giveand receive tailored healthcare information about their respectivehealth conditions and stays. Other such media and communication systemsoperate within other institutions such as hotels, businesses, schools,homes, and other facilities and locations.

Among the persistent problems in operating such local media andcommunications systems are the limitations of the user remote controldevice in operating end user devices such as television sets. Forexample, in a hospital setting, a user will often utilize a “pillowspeaker” remote control device, typically hardwired into each system.Other remote controls, utilizing infrared signal technology, are alsoutilized.

Significant limitations exist with the control functionality of pillowspeaker and other remote control devices. For example, patients havevarying needs and gross motor and fine motor abilities, and manipulatingthe often large and clumsy pillow speakers and other remote controldevices can be challenging. Furthermore, with respect to pillowspeakers, such devices often introduce a lag time and the controlbuttons can be difficult to press. Pillow speakers and other remotecontrol devices also have a limited number of buttons, limiting theamount of controls the user can utilize to control the endpoint device.

Other problems include certification of new TV models, which change at avery frequent pace, certification and corresponding firmware changes toTelevision Control Modules and Set Back Boxes to allow control of new TVmodels, the fact that different codes-sets on pillow speakers work withdifferent TV manufacturers/models, limitations in the number ofbuttons/codes or available functionality based on Pillow Speakermanufacturer agreements with Nurse Call systems, the typically lengthyprocess for creation of new pillow speakers and/or overlays, lack ofease of navigation within control menus for certain patient populations,due to the construction of the devices in accordance with healthcarestandards which require that the devices be cleaned frequently.

Other remote controls, for example remote controls utilizing infraredsignals, suffer from similar problems in that different remote controlswork with different TV models/manufacturers, having only a limitednumber of user buttons, lack of ease in navigating through menu screenssince there needs to be direct line-of-sight between the remote and theTV, and need to meet healthcare standards in their ability to becleaned.

The present invention solves these problems with a significantadvancement in local system control technology. Specifically, as shownand described herein, the present invention utilizes a mobileapplication and wireless local area networking systems to controlnavigation at the application server level, allowing for an advancedability to navigate, manage content, and communicate within a givenmedia and communications system. Overall, the present invention istherefore a significant advancement in the field institution computertechnology allowing users to achieve key outcomes.

SUMMARY OF THE INVENTION

In accordance with one embodiment of the invention, a system is providedwherein the system comprises a database, wherein said database containsuser data; an interface engine, wherein said interface engine isconfigured to communicate with said database and parse said user data;an application server, wherein said application server is configured tocommunicate with said interface engine; a user device, wherein said userdevice is configured to receive and display said parsed data, receiveuser-provided information, and send said user-provided information tosaid application server; and wherein said application server isconfigured to automatically update a display of said user device withone or more aspects of said parsed data, receive user-providedinformation from said user device, and provide said user-providedinformation to said interface engine for updating said database.

In another exemplary embodiment of the invention, a method is providedcomprising receiving user data from a database, parsing said user datato create parsed data; storing said parsed data; sending admission datato an application server; confirming that said admission datacorresponds to an available user device; sending said parsed data tosaid device so that said device can display said parsed data;automatically updating said parsed data to create updated parsed data;and automatically displaying said updated parsed data on said display ofsaid device.

In another exemplary embodiment of the invention, a system is providedcomprising an application server, a wireless local area network, a userdevice, an endpoint device, wherein said user device is configured tosend one or more commands to said application server over said localarea network, said endpoint device is configured to receive and executesaid commands as instructed from said applications server, and saidendpoint device is configured to display media content on a display ofsaid endpoint device corresponding to said commands.

In another exemplary embodiment of the invention, a method is providedcomprising communicating with a facility application program over awireless local area network, wherein such communication is performed bya user application program operating on a user device; authenticatinguser information of a user of said user device, wherein saidauthentication is performed by said facility application program;pairing said user device with an endpoint device, wherein said endpointdevice is configured to display media content; displaying one or morecontrol icons on said user device, wherein said one or more controlicons are configured to receive command instructions from said user ofsaid user device; sending one or more commands to said facilityapplication program through haptic contact engagement with said one ormore control icons; and controlling said endpoint device to display saidmedia content corresponding to said one or more commands.

The above and other various aspects and embodiments are described belowwith reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form partof the disclosure, help illustrate various embodiments of the presentinvention and, together with the description, further serve to describethe invention to enable a person skilled in the pertinent art to makeand use the embodiments disclosed herein.

In the drawings, like reference numbers indicate identical orfunctionally similar elements.

FIG. 1 illustrates an interactive communications and control systemwithin a healthcare institution as shown and described herein.

FIG. 2 illustrates another aspect of an interactive communications andcontrol system within a healthcare institution, as shown and describedherein.

FIG. 3 illustrates another aspect of an interactive communications andcontrol system within a healthcare institution, as shown and describedherein.

FIG. 4A illustrates another aspect of an interactive communications andcontrol system within a healthcare institution, and devices utilized inthat system, as shown and described herein.

FIG. 4B illustrates another aspect of devices utilized by an interactivecommunications and control system within a healthcare institution, asshown and described herein.

FIG. 4C illustrates another aspect of devices utilized by an interactivecommunications and control system within a healthcare institution, asshown and described herein.

FIG. 5A illustrates a user interface utilized by an interactivecommunications and control system within a healthcare institution, asshown and described herein.

FIG. 5B illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5C illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5D illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5E illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5F illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5G illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5H illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 5I illustrates another aspect of a user interface utilized by aninteractive communications and control system within a healthcareinstitution, as shown and described herein.

FIG. 6 illustrates a method for the interactive sharing of informationwithin a healthcare institution, as shown and described herein.

FIG. 7 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 8 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 9 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 10 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 11 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 12 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 13 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 14 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 15 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 16 illustrates another aspect of a method for the interactivesharing of information within a healthcare institution, as shown anddescribed herein.

FIG. 17 illustrates a method for the interactive sharing of informationwithin a healthcare institution, as shown and described herein.

FIG. 18 illustrates a system for the control of media and communicationssystems, as shown and described herein.

FIG. 19A illustrates another aspect of a system for the control of mediaand communications systems as shown and described herein.

FIG. 19B illustrates another aspect of a system for the control of mediaand communications systems as shown and described herein.

FIG. 20 illustrates another aspect of a system for the control of mediaand communications systems as shown and described herein.

FIG. 21 illustrates a method for the control of media and communicationssystems, as shown and described herein.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 1, an embodiment of an electronic communicationssystem 100 for the interactive sharing of information within ahealthcare institution is shown.

The system 100 includes a number of hardware and software componentsdesigned to communicate across a local area network 102, wide areanetwork, or other functional network to allow for the interactivesharing of information relating to a patient's care and stay at ahealthcare institution.

In this embodiment, as will be described in more detail below, thecomponents of the system 100 include an integration server 106, anapplication server 108, a database server 110, a management server 112,a streaming server 114, and one or more types of user devices including,but not limited to, a standard television 116, a smart television 118, abedside terminal 120, a smart tablet 122, a smart phone 124, and adigital white board terminal 126.

These and other system 100 hardware and software components areconfigured to communicate with an electronic medical records (EMR)system 104, typically belonging to or otherwise operated by thehealthcare or other institution where the system 100 is implemented. Itwill be understood that any number of other like components can be addedto the system 100 to accomplish the objectives of the system 100 asdescribed herein. It will also be understood that an edge server 115 canalso be utilized when one or more of the other system 100 servers andother components are located off-site. The edge server 115 is configuredto allow communication between such offsite system 100 components andonsite system 100 components in order to allow proper functioning of thesystem 100 as described herein.

Referring now to FIG. 2, another aspect of the system 100 is shown.Here, each healthcare institution will have one or more EMR systems 104that are institution-based full applications that store, have access to,and manage multiple data sets relating to each patient based on theworkflows in a given healthcare institution or healthcare system. Itwill be understood that the EMR system 104 could utilize local servers,third party servers, or other components or databases configured tostore, distribute and otherwise manage such data. It will be furtherunderstood that the EMR system 104 can reside on a single server orlocation, or reside on multiple servers or locations located within oroutside of the facility in the vicinity of the system 100 or not.

The EMR system 104 contains information relating to a number ofcategories of patient and health information. This information isexchanged with system 100 through a variety of messages and transactiontypes relating to, among other things, patient ADT data (admissions,discharge, transfer and other patient-related data) 202, patientmedication data 204, nursing assessment data 206, orders and resultsdata 208, diet orders data 210, and patient education data 212 data.

In addition, the system 100 enhances the patient experience by providingpatients with the ability to submit requests and feedback data 214,submit meal orders data 216, and submit HVAC control data (e.g.,temperature control) 218 to the system 100 through user interfaces ofeach patient's device (e.g., smart television 118). This data, and otherfeedback data (e.g., relating to patient education feedback data 212) ischanneled through the application server 108 and/or integration server106, and exchanged with the EMR system 104, third party vendorapplications, or other applications as appropriate.

The system 100 also enhances data received from the EMR system 104 whenthat data 220 might not be meaningful to a patient in the format inwhich it is stored on the EMR system 104. For example, patient dietorders data 210 received from the EMR system 104 as “NPO2” might bemapped in the EMR system 104 as: “Nil per os.” “Nil per os” is a Latinphrase meaning “nothing by mouth” restricting all oral food and fluids,and the system 100 is configured to present that data in plain English,or other languages, to the patient on one or more system devices.

Similarly, drug information 204 received from the EMR system 104 mighthave a variety of codes that the system 100 translates into plainlanguage. For example, the EMR system 104 might provide a code:23490647801, which the system will translate into “Warfarin” (thenational NDC code for Warfarin is 23490647801). The system 100 isconfigured to query such information from third party vendors to obtainand display information in a patient-friendly format like “What is thedrug used for”, “What are some adverse effects,” and display thecorresponding information in plain language on one or more of thepatient devices.

It will be understood that the above categories of information areprovided as examples, and other categories of information could also bethe subject of the operation of the system 100, devices and methods asdescribed herein.

The system 100 also includes an integration server 106. In thisembodiment, the integration server 106 is a virtual machine serverconfigured to utilize one or more storage memory components 222 andutilize, interact with, or otherwise reside within the infrastructure ofeach given healthcare institution.

The storage memory components 222 can include one or more computerreadable storage mediums 224 designed to store executable instructionssuch as computer code, and one or more other storage memory components226 designed to store other data utilized during the operation of thesystem 100.

The integration server 106 is configured with a third party interfaceengine 230 that allows, in conjunction with an integration applicationprogram 228, for the receiving, sending and separation of a variety ofmessages and message types to and from the EMR system 104 and othersystem 100 servers and components using a variety of standards andprotocols.

The integration application program 228 is also stored on theintegration server 106 on one or more of its storage memory components222, such as a computer readable storage medium 224, and is configuredto communicate with the interface engine 230 to allow for the receiving,sending and separation of a variety of messages and message types to andfrom the EMR system 104 and other system 100 servers and componentspursuant to the operation of the system 100 as described herein.

In the present embodiment, the interface engine 230 contains channels orpipes 232, which communicate with the EMR system 104, and containoperational instructions to access, parse and update informationtransacted with the EMR system 104 and other third party systems 234.Such information includes, but is not limited to, the ADT data(admissions, discharge and transfer) 202, medications data 204, nursingassessment data 206, orders and results data 208, diet orders data 210,education data 212, patient requests and feedback data 214, patient mealorder 216 data, HVAC control data 218, patient friendly medication data220, and other data 236.

The integration application program 228 is configured to communicatewith the interface engine 230 and create and store parsed data setscorresponding to the accessed data sets, including parsed ADT data(admissions, discharge and transfer) 202, medications data 204, nursingassessment data 206, orders and results data 208, diet orders data 210,education data 212, patient requests and feedback data 214, mealordering data 216, HVAC data 218, patient friendly medication data 220,and other corresponding data 236.

It will be further understood that the integration application program228 operating on the integration server 106 is configured to act uponthe parsed data identified above in a number of different ways dependingupon the type and complexity of the messages and data in each data set.In some cases, the parsed data will be stored (on any of the storagememory components of the system 100). In other cases, the parsed datawill be sent to the application server 108 for utilization in the system100.

It will be further understood that the integration application program228 operating on the integration server 106 is configured to receivedata from the various system components (e.g., the application server108) and in some circumstances communicate data, including updatedinformation, to the EMR system 104.

The integration server 106 and integration application program 228 arealso configured to communicate with the other servers, programs, andcomponents of the system 100 across the network 102 in accordance withthe operation of the system 100 as described herein.

Referring now to FIG. 3 another aspect of the system 100 is shown. Here,the system 100 also includes an application server 108. In thisembodiment, the application server 108 is a virtual machine serverconfigured to utilize one or more storage memory components 302 andutilize, interact with, or otherwise reside within the infrastructure ofeach given healthcare institution.

The storage memory components 302 can include one or more computerreadable storage mediums 304 designed to store executable instructionssuch as computer code, and one or more other storage memory components302 designed to store other data utilized during the operation of thesystem 100.

The application server 108 is configured to store a system applicationprogram 306 on one or more of its storage memory components 302, such asa computer readable storage medium 304. The system application program306 contains operational instructions to manage the operation of thesystem 100, including, but not limited to, sending, receiving andmanaging information amongst the various components of the system 100 toensure proper operation of the system 100.

The system application program 306 is also configured to call,communicate with, or otherwise rely upon several other servers andprograms within the system 100. For example, the system applicationprogram 306 is configured to call, communicate with, or otherwise relyupon integration server application program 228 residing on theintegration server 106. This communication is important for, among otherthings, the sending, receiving and updating of data transacted with thefacility EMR system 104, user interfaces and other components of thesystem 100.

The system application program 306 is also configured to call,communicate with, or otherwise rely upon a database server 110. In thisembodiment, the database server 110 is a virtual machine serverconfigured to store various system and patient data 320 including textand media (e.g., video) content, as well as certain operational computercode 308, on one or more storage memory components 310. The databaseserver 110 is also configured to utilize, interact with, or otherwisereside within the infrastructure of each given healthcare institution.

The system application program 306 is also configured to call,communicate with, or otherwise rely upon a management server 112. Inthis embodiment, the management server 112 is a virtual machine serverconfigured to store various system tools 315, as well as certainoperational computer code 312, on one or more storage memory components314. The management server 112 is also configured to utilize, interactwith, or otherwise reside within the infrastructure of each givenhealthcare institution.

The system application program 306 is also configured to call,communicate with, or otherwise rely upon a streaming server 114. In thisembodiment, the streaming server 114 is a virtual machine serverconfigured to store video and other media content, tools to assist withthe streaming of video content, as well as certain operational computercode 316, on one or more storage memory components 318. The streamingserver 114 is also configured to utilize, interact with, or otherwisereside within the infrastructure of each given healthcare institution.

It will be further understood that the application program 306 operatingon the application server 108 is configured to act upon the data itaccesses and receives in accordance with the desired functioning of thesystem 100. In some cases the data will be stored, in other caseslogical operations will be performed on the data, and in other cases thedata will be relayed to other system 100 components for updating andexecution.

Referring now to FIG. 4A, another aspect of the system 100 is shown.Here, the system 100 includes various user, or endpoint, devicesconfigured to allow end users (for example, patients, family members ofpatients, and healthcare institution personnel) to interact with andotherwise utilize the system 100.

The user devices can be in the form of a television 116, bedsideterminal 120, and a dedicated digital white board terminal 126, eachwith an attendant television program box 402. In this embodiment, eachtelevision program box 402 is configured to store an executable program404 that interfaces with the system application program 306 and allowsthe system application program 306 to communicate with the referenceddevices and display the system's graphical user interface 406 on thedisplay 408 of each device. It will be understood that with respect tothe white board terminal 126, that terminal is configured, in oneembodiment, to display key updated patient information on an ongoingbasis in real time.

Similarly, the system 100 can also utilize a smart television 118, smartphones 124, smart tablets 122, or other intelligent devices that storean executable program 410 built into or otherwise stored upon eachdevice, obviating the need for a program box such as program box 402containing program 404.

In this embodiment, the executable programs 410 are configured tointerface with the system application program 306 over the network 102and allow the system application program 306 to communicate with thesmart devices 118, 122 and 124 and display the system's graphical userinterface 406 on the display 408 of each of the smart devices 168, 170and 172.

It will be understood that the executable programs 404, 410 operating onor in conjunction with each user device are configured to also receiveuser input, such that each user of each device can input informationactively (e.g., typing commands, selecting menu items, typing messages)or passively (e.g., tracked viewing habits), and provide (either sendingor allowing access to) that information to the system applicationprogram 306 over the local area network 102, such that the systemapplication program 306 can utilize that information in accordance withthe operation of the system 100 described herein.

At this stage, it will be understood that the executable program 410operating on the smart television 118 is configured to requestinformation from the application server 108, including, but not limitedto, information shown on the menu of each display (e.g., medication data204, nursing assessment data 206, orders and results data 208, dietorders data 201, patient education data 212, patient requests andfeedback data 214, meal ordering data 216, HVAC data 218, patientfriendly medication data 220, and other data 236). It will be understoodthat the executable program 410 operating on the smart television 118 isconfigured to display this information on the user interface 408 locatedon the display 408 of the smart television 118, as the patient navigatesthrough the various menu items.

It will be further understood that the executable program 410 operatingon the smart television 118 is also configured to send active andpassive information to the application server. Examples of activeinformation include user-generated information (e.g., patient requestsand feedback, meal ordering, HVAC requests) and passive user information(e.g., the time amount of a particular video a patient has watched, howmany videos the patient has watched, how engaged is the patient with thevarious menu items in the system).

Referring now to FIG. 4B, further description of the components of asmart television 118 is shown. In this embodiment, the smart television118 includes a number of components including, but not limited to, adisplay 408, executable program 410, processor 420, power supply(battery or hardwire) 422, storage memory component 424, remote controlcontroller 426, camera (two-way video and audio capability) 428, andcamera/video controller 430. It will be understood that these areexamples of components utilized with the system 100, but it will befurther understood that the smart television 118 can include any numberof other components that can be utilized by the system 100 in themanners described herein and otherwise.

The executable program 410, tools, and APIs are stored on the device(e.g. smart television 118) allowing the executable program 410 tocommunicate with and control the device (including the device hardwarecomponents (e.g., to turn the device 118 on/off)). This executableprogram 410 for each device has the ability to recognize the device type(in this case a smart television 118) and apply the appropriatecontrols. The executable program 410 is configured to load/reload fromthe application server 108 for various activity including, but notlimited to, patient admission and discharge, and other roadmaps specificto the healthcare industry, and to have constant communication with therest of the system 100.

Referring now to FIG. 4C, further description of the components of amobile phone 124 or tablet 122 devices is shown. In this embodiment,mobile phone 124 and/or tablet 122 includes a number of componentsincluding, but not limited to, a display 408, executable program 410,processor 432, power supply (battery or hardwire) 432, storage memorycomponent 436, camera (two-way video and audio capability) 438, andcamera/video controller 440, wireless processor 442, touch sensors 444and touch controller 446. It will be understood that these are examplesof components utilized with the system 100, but it will be furtherunderstood that the mobile phone 124 or tablet 122 devices can includeany number of other components that can be utilized by the system 100 inaccordance with the manners described herein and otherwise.

It will be further understood that each of the system 100 componentscontains non-transient computer readable storage mediums, or otherstorage mediums, on which such components are capable of storinginformation including executable and non-executable computer code,related source code, course code, binary files, application programinterfaces (APIs), and/or other executable code or instructions.

It will be further understood that communication between any or all ofthe system 100 components can be performed through operation of one ormore application program interfaces (APIs) contained within the system100 allowing communication between system 100 components over a localarea network 102, or wide area network when accessing components orinformation residing outside of the facility.

It will be further understood that the server arrangements describedherein are provided as examples, but the arrangement of servers could bemade in a multitude of other ways, including through one or moreadditional virtual machine servers with storage memory componentsoperating within a cloud-based server network, and/or other serverarrangements that would allow the system 100 to operate in the mannersdescribed herein.

It will be understood that the system's 100 utilization of virtualservers to operate the system 100 as described herein, in combinationwith the integration program 228, application program 306, and othercomponents and applications of the system 100, provides the system 100with many significant enhancements.

For example, this configuration, as described herein, provides thesystem 100 with the enhanced ability to operate within a broad range ofdiverse host environments and datacenters. It also provides the system100 with enhanced disaster recovery, uptime and scalability. It alsoreduces the institution's data center footprint and allows for serverconsolidation. It also provides for easier maintenance, includingenhanced ability to install a virtual machine server from an existingcopy/template, re-installing, backup and movement to a different server.It also allows for maintaining scaled down test systems, and applyingsecurity patches in compliance with the policies of each institution.

It also eliminates the need to supply hardware on site, and provides aspecialized information system unique to the healthcare industry(eliminating the need to adapt applications built to serve datacenterinfrastructure of other industries, such as the hotel industry). It alsoeliminates the need to draw from disparate hardware and software sourcesand third party proprietary equipment to operate the system 100. It alsoallows for easier management and integration of endpoints (e.g., devicessuch as tablets, cell phones, televisions, etc.).

Moreover, it also eliminates the need to use specific video streaminghardware and rely on third party video streaming vendors. It also andallows the system 100 to use newer technologies that support lower andvariable bandwidth for display on different types of portable devices,which further allows for a greater number of simultaneous video streamsand hence serve a larger number of rooms/beds. It also provides theflexibility to separate out components to the local facility per therequirements of each institution (for example, in a typical deployment,a video streaming server is placed at a local facility, which saves onvideo bandwidth over the wide area network, or the system could flexbetween streaming video from the datacenter and local facility based onavailability). It will be understood that these are examples ofenhancements that the current invention provides to the computertechnology previously utilized for such applications, and that otherenhancements also exist inherently or otherwise.

Referring now to FIG. 5A-5J, several embodiments of the user interface406 displayed by the system application program 306 on each user deviceis shown. In these embodiments various menu items appear to a givenuser. In FIGS. 5A-F, these menu items and other offerings on the userinterface 406 represent an entire feature set 501, providing the userwith a multitude of offerings within the user interface 406.

It will be understood that one example of a feature set could be all ofthe elements and menu offerings shown and described in connection withFIGS. 5A-5F, and could also include many other features offered to apatient through the user interface 406 viewable on the display of theterminal or device. In the embodiments of FIGS. 5A-5F, the user canselect actionable menu items in any manner allowed by the subjectdevice, including, but not limited to, selection through remote control(such as through a television), selection through haptic contactengagement (such as through contact on the display of a smart phone orsmart tablet), or selection through point-and-click (such as through acomputer mouse and computer).

With respect to FIGS. 5G-5I, an embodiment of a graphical user interface406 for a digital white board 126 is shown. It will be understood thatthis information is designed to display key patient information in realtime, and it utilized by the patient and healthcare professionals, andhas distinct functionality from the feature set displayed by the userinterfaces set out in 5A-5F.

Referring now to FIG. 5A, an embodiment of a system user interface 406is shown. Here, patient name and room information 502 is displayed,along with the day, date and time 504. General menu items relating toenjoyment 506, meals 508, stay 510, care 512, and personalizedinformation 514 are displayed. The enjoyment menu item 506 can havesubset menu items for the patient to choose from including generaltelevision 516, free movies 518, scenic television 522, games and trivia524, internet 526, and sleep-related content 528. It will be understoodthat once selected, each actionable menu item will direct the patient toa new page allowing that user to further interact with the system 100with respect to subject matter relating to enjoyment.

Referring now to FIG. 5B, another embodiment of a system user interface406 is shown. Here, the meals menu item 508 can have subset menu itemsfor the patient to choose from including ordering food based on theirdiet restrictions 530, identifying local restaurants 532, and viewingcontent from designated food channels 534. It will be understood thatonce selected, each actionable menu item will direct the patient to anew page allowing that user to further interact with the system 100 withrespect to subject matter relating to meals.

Referring now to FIG. 5C, another embodiment of a system user interface406 is shown. Here, the stay menu item 510 can have subset menu itemsfor the patient to choose from including key institution information536, institution directory 538, patient services 540, spiritual support542, room temperature 544, special requests 546, and patient feedback548. It will be understood that once selected, each actionable menu itemwill direct the patient to a new page allowing that user to furtherinteract with the system 100 with respect to subject matter relating tothe patient's stay.

Referring now to FIG. 5D, another embodiment of a system user interface406 is shown. Here, the care menu item 512 can have subset menu itemsfor the patient to choose from including health education library 550,digital whiteboard 552, medication 554, patient-specific chart 556, mindand soul 558, care channel (relaxing content) 560, and dischargechecklist 562. It will be understood that once selected, each actionablemenu item will direct the patient to a new page allowing that user tofurther interact with the system 100 with respect to subject matterrelating to care.

Referring now to FIG. 5E, another embodiment of a system user interface406 is shown. Here, the personalized information menu item 514 can havesubset menu items for the patient to choose from including specificallyassigned educational videos 564, patient journal 566, system settings568, analogous patient cases 570, and tailored entertainment 572. Itwill be understood that once selected, each actionable menu item willdirect the patient to a new page allowing that user to further interactwith the system 100 with respect to subject matter relating topersonalized patient information.

Referring now to FIG. 5F, another embodiment of a system user interface406 is shown. Here, a virtual white board interface 574 is shown, beingdisplayed within the navigable user interface 406. Here, the informationdisplayed includes detailed information concerning a patient's care team576, daily appointments, tests and activities 578, special diets andallergies 580, pain levels and requests for special services 582, andmedications, test results, and other clinical information 584.

Referring now to FIG. 5G, an embodiment of a system user interface 406for a digital white board 126 is shown. Here, the information displayedincludes detailed information concerning a patient's care team 585,physiology 586, diet 587, activities and schedule 588, tests 589, andother clinical information 595. Subject matter tabs 594 for each set ofdata are provided on the display of the digital white board 126.

Referring now to FIG. 5H, another embodiment of a system user interface406 for a digital white board 126 is shown. Here, the informationdisplayed includes detailed information concerning a patient'smedication 590, which could be a variety of medications falling underdifferent fields 596. Subject matter tabs 594 for each set of data areprovided on the display of the digital white board 126.

Referring now to FIG. 5I, another embodiment of a system user interface406 for a digital white board 126 is shown. Here, the informationdisplayed includes detailed information concerning key medical notes 591for the patient, including a general category of useful clinicalinformation 592, as well as other notes 593. Subject matter tabs 594 foreach set of data are provided on the display of the digital white board126.

Referring now to FIG. 6, an embodiment of an interactive sharing ofpatient-related information method 600 is shown.

In step 602 of method 600, the integration application program 228operating on the integration server 106 receives the ADT data 202,medications data 204, nursing assessment data 206, orders and resultsdata 208, diet ordering data 210, education data 212, patient requestsand feedback data 214, meal ordering data 216, HVAC (temperaturecontrol) data 218, patient friendly medication data 220, and other data236 from the institution's EMR system 104.

In step 604 of method 600, the integration application program 228operating on the integration server 106 parses the ADT data 202,medications data 204, nursing assessment data 206, orders and resultsdata 208, diet ordering data 210, education data 212, patient requestsand feedback data 214, meal ordering data 216, HVAC (temperaturecontrol) data 218, patient friendly medication data 220, and other data236.

In step 606 of method 600, the integration application program 228operating on the integration server 106 sends the parsed ADT data 202 tothe application server 108. It will be understood that the ADT data 202includes admission, discharge, transfer, and room information for eachpatient, as well as other patient data including, but not limited to,the patient's name, identifying information, demographics, physiciansassigned to the patient, and other relevant information for thatpatient. The integration application program 228 passes all of thisinformation to the application server 108 and the application server 108stores that information as part of the patient's record.

In step 608 of method 600, the system application program 306 operatingon the application server 108 verifies whether the room identified inthe parsed ADT data 202 for a given patient is available. If such roomis available, the method 600 continues. If not, the system applicationprogram 306 notifies the integration application program 228 and themethod 600 ceases until the ADT data 202 is updated or otherwisecorrected and the method 600 commences again beginning at step 602. Itwill be understood that the terminals 120 and other in-room devices areassociated with certain rooms and beds in the institution during theinitial configuration of the system 100. If for some reason a terminal120 or device is not properly associated with a certain room and bed, oris replaced, the system application program 306 will provide a messageof “Service Not Available” viewable on the user terminal or device,until the terminal or device is properly assigned to the appropriateroom and bed.

In step 610 of method 600, if verified, the system application program306 operating on the application server 108 enables the one or moredevices and/or terminals in the assigned room to receive and otherwisedisplay the patient-related information from the system 100. In thisembodiment, the method 600 will utilize a single smart television 118assigned to a certain room for a certain patient. However, it will beunderstood that multiple devices configured to be utilized by the system100 and users of the system 100 could also be used as a terminal ordevice component of the system 100 in the manner described herein.

In step 612 of method 600, the system application program 306 operatingon the application server 108 sends or pushes a notification to thesmart television 118 that a certain patient is assigned to that device.

In step 614 of method 600, the system application program 306 operatingon the application server 108 sends or pushes a command to the smarttelevision 118 that the smart television 118 make the appropriatefeature set 501 available on the smart television 118 for that patient.

In step 616 of method 600, the executable program 410 operating on thesmart television 118 displays the feature set 501 on the user interface408 located on the display 408 of the smart television 118. It will beunderstood that the feature set 501 in this embodiment includes, but isnot limited to, the feature set 501 shown and described in FIG. 5,including all menu items, date and time information, and otherinformation that the system application program 306 operating on theapplication server 108 sends to and receives from the smart television118 to populate and otherwise link to the menu items on the userinterface 406 as the user operates the system 100.

It will be understood that with respect to other smart devices, such assmart phones 124 and smart tablets 122, such devices are configured toreceive a verification code from the system 100 to confirm the devicebelongs to that patient and is allowed access. It will be furtherunderstood that such access will be restricted to the patient room only,and would not be allowed once the device is removed from the roomthrough a combination of local WiFi or geo-location mechanism, in whichcase the smart phones 124 and smart tablets 122, could contain generalinformation and media but no patient-specific information.

At this stage, it will be understood that the smart television 118 isnow connected to and otherwise operational within the system 100. Itwill be further understood that any number of different methods exist inconnection with the operation of the system with respect to each featureof the feature set 501. For example, the system components can beconfigured to operate certain modules of each feature set 501.

Accordingly, in step 618 of method 600, the system 100 operates afeature set based on medication data 204, more fully shown and describedin reference to FIG. 7.

In step 620 of method 600, the system 100 operates a feature set basedon nursing assessment data 206, more fully shown and described inreference to FIG. 8.

In step 622 of method 600, the system 100 operates a feature set basedon orders and results data 208, more fully shown and described inreference to FIG. 9.

In step 624 of method 600, the system 100 operates a feature set basedon diet orders data 210, more fully shown and described in reference toFIG. 10.

In step 626 of method 600, the system 100 operates a feature set basedon patient education data 212, more fully shown and described inreference to FIG. 11.

In step 628 of method 600, the system 100 operates a feature set basedon patient requests and feedback data 214, more fully shown anddescribed in reference to FIG. 12.

In step 630 of method 600, the system 100 operates a feature set basedon patient meal ordering data 216, more fully shown and described inreference to FIG. 13.

In step 632 of method 600, the system 100 operates a feature set basedon patient HVAC control requests 218, more fully shown and described inreference to FIG. 14.

In step 634 of method 600, the system 100 operates a feature set basedon patient bedside monitoring requests, more fully shown and describedin reference to FIG. 15.

In step 636 of method 600, the system 100 operates a feature set basedon patient entertainment, more fully shown and described in reference toFIG. 16.

In step 638 of method 600, the information contained in each feature set501 described herein is continually updated as each of the feature set501 menu items and other items are accessed. It will be understood thatthe updating of the underlying data occurs automatically based oncommunication between the various system components, including betweenthe application server 108, integration server 106, and facility EMRsystem 104.

In step 640 of method 600, the information contained in the facility EMRsystem 104 is continually updated based on information received from theintegration program 228 operating on the integration server 106 (basedon information received from other system 100 components including theapplication server 108) based on certain activities by the patient.

It will be further understood that the modules described herein areprovided as examples, and that other modules and features could also beunderstood by one of ordinary skill in the art to be within the scope ofthe invention as described herein.

Referring now to FIG. 7, steps for a medication data module of thepresent invention is shown and described in accordance with method 700.In step 702 of method 700, the executable program 410 operating on thesmart television 118 requests patient medication data 204 from theapplication server 108 as a result of the user selection of themedication menu item 554.

In step 704 of method 700, the system application program 306 operatingon the application server 108 sends the patient medication data 204 tothe smart television 118. It will be understood that the integrationprogram 228 operating on the integration server 106 parses themedication data 204 orders received from the EMR system 104 for keyidentifying information that is then used to query systems from othervendors to obtain, parse and store patient-friendly information. Theintegration program 228 operating on the integration server 106 sendsthis information to the application server 108. The application program306 operating on the application server 108 sends the patient medicationdata 204 to the smart television 118 for display on the user interface406 on the in-room device. Other activities such as immediatediscontinuation of certain medications, updates to discontinuation datesin the future, and other key information items relating to patientmedication data 204 are updated and/or modified in the system 100accordingly.

In step 706 of method 700, the executable program 410 operating on thesmart television 118 displays the medication data 204 on the display 408of the smart television 118.

Referring now to FIG. 8, steps for a nursing assessment data module ofthe present invention is shown and described in accordance with method800. In step 802 of method 800, the executable program 410 operating onthe smart television 118 requests nursing assessment data 206 from theapplication server 108 as a result of the user selection of the nursingassessment data from the care menu item 512.

In step 804 of method 800, the system application program 306 operatingon the application server 108 sends the nursing assessment data 206 tothe smart television 118. It will be understood that the nursingassessment data 206 includes, but is not limited to, nursing assessmentsand documentation including patient activity, goals, pain scale, andother data.

It will be further understood that the integration program 228 operatingon the integration server 106 evaluates and acts upon the nursingassessment data 206 received from the EMR system 104. This includesassessment of the type of information received from the EMR system 104,updating the patient's clinical records within the system 100appropriately, referencing patient friendly text as well as visual cues(fall risk, hearing aid, etc.) that is extensively mapped in the system100 and database 110 design along with rules to handle updates for thedifferent types of activity generated. For certain institutions, EMRsystems 104, staff assignments and shifts might also be part of theserecords.

In step 806 of method 800, the executable program 410 operating on thesmart television 118 displays the nursing assessment data 206 on thedisplay 408 of the smart television 118. It will be understood that thenursing assessment data 206, as well as other patient-related datareferenced herein, including in connection with FIGS. 5G, H and I, canalso be displayed on the digital white board 126. In that configuration,the system application 306 operating on the application server 108causes the information displayed on the digital white board 126 to beupdated automatically in real time based on information changes at theEMR system level 104.

Referring now to FIG. 9, steps for an orders and results data module ofthe present invention is shown and described in accordance with method900. In step 902 of method 900, the executable program 410 operating onthe smart television 118 requests orders and results data 208 from theapplication server 108 as a consequence of the user selection of theorders and results data 208 from the care menu item 512.

In step 904 of method 690, the system application program 306 operatingon the application server 108 sends the orders and results data 208 tothe smart television 118. It will be understood that the orders andresults data 208 includes, but is not limited to, data relating toorders for patients such as radiology (X-Rays, CT scans, MRIs),cardiology (ECG), and laboratory tests. It will be further understoodthat this information originates in the institution EMR system 104 andis parsed by the integration application program 228 and sent to andstored by the application server 108, such that the application program306 operating on the application server 108 can send the data to thesmart television 118 in accordance with the invention as describedherein.

In step 906 of method 900, the executable program 410 operating on thesmart television 118 displays the orders and results data 208 on thedisplay 408 of the smart television 118.

Referring now to FIG. 10, steps for a diet orders data module of thepresent invention is shown and described in accordance with method 1000.In step 1002 of method 1000, the executable program 410 operating on thesmart television 118 requests the diet orders data 210 from theapplication server 108 as a result of the user selection of the dietorders data 210 from the meals menu item 508.

In step 1004 of method 1000, the system application program 306operating on the application server 108 sends the diet orders data 210to the smart television 118. It will be understood that the diet ordersdata 210 includes, but is not limited to, recommended or required dietorder from healthcare personnel based on a patient's condition (e.g.,“no eating for 12 hours before surgery,” “no sugar,” “fluids only”). Itwill be further understood that diet orders data 210 received from theEMR system 104 can have certain codes that are mapped to patientfriendly information within the system 100. The application program 306operating on the application server 108 looks up these codes and storesthese codes against the patient's clinical information for display onthe user interface 406 on the in-room device.

In step 1006 of method 1000, the executable program 410 operating on thesmart television 118 displays the diet orders data 210 on the display408 of the smart television 118.

Referring now to FIG. 11, steps for patient education feature of thepresent invention is shown and described in accordance with method 1100.In step 1102 of method 1100, the executable program 410 operating on thesmart television 118 requests patient education data 212 from theapplication server 108 as a result of the user selection of patienteducation data 212 from the personalized information menu item 514.

In step 1104 of method 1100, the system application program 306operating on the application server 108 sends the requested patienteducation data 212 to the smart television 118. It will be understoodthat the data 212 is available to the system application program 306because the integration program 228 operating on the integration server106 continually receives relevant education data 212 from the EMR system104, parses that data, and automatically sends that parsed data to theapplication server 108.

It will be further understood that the patient education feature of thesystem 100 is functionally bi-directional. For example, patienteducation data 212 (including videos, articles, and other information)can be initiated by institution professionals and staff at the EMRsystem 104 level. In putting the education data 212 together,institution professionals can draw from multiple sources including, butnot limited to, physician orders, problem lists, medications,educational videos, and other sources.

It will be further understood that patient education data 212 content tobe viewed (e.g., an educational video) is mapped in the system 100 alongwith questions on who is going to view the content and followed byquestions to document patient comprehension. It will be furtherunderstood that the patient education data 212 can be provided in theform of educational video packets, or highly customized, prepared andvetted video and/or textual information relating to the specificcondition, procedure, or other health-related item specifically relatingto each patient, to be provided to each patient at the proper time.

In step 1106 of method 1100, the executable program 410 operating on thesmart television 118 displays the patient education data 212 on thedisplay 408 of the smart television 118. It will be understood that whena patient views the appropriate patient education data 212 contentthrough the user interface 406, information relating to that viewing(e.g., if a video, whether viewing of a video was completed, and if not,how long the video was viewed) is passed back to the application server108.

In step 1108 of method 1100, the executable program 410 operating on thesmart television 118 sends the user input relating to the patienteducation data 212 to the application server 108.

In step 1110 of method 1100, the system application program 306operating on the application server 108 sends the user input relating tothe patient education data 212 to the integration server 106 where theproper message format is created in the interface engine 230.

In step 1112 of method 1100, the integration application program 228operating on the integration server 106 sends the user input relating tothe patient education data 212 to the EMR system 104 for documentation.

Referring now to FIG. 12, steps for a patient requests and feedback ofthe present invention is shown and described in accordance with method1200. In step 1202 of method 1200, the executable program 410 operatingon the smart television 118 sends patient requests and feedback data 214to the application server 108 as a result of the user sending such datathrough the appropriate user menu item.

In step 1204 of method 1200, the system application program 306operating on the application server 108 sends the patient requests andfeedback data 214 to the integration server 106 where the proper messageformat is created in the interface engine 230.

It will be understood that the patient requests and feedback data 214are messages that result from a patient selecting an item on the userinterface 406 and are sent from there to the application server 108which stores relevant information and sends that information to theintegration server 106. It will be further understood that patientrequests include, but are not limited to, any number of patientrequests, such as wanting to speak to a pharmacist, wanting to speakwith clergy, wanting a pillow, requesting bedside delivery of dischargemedications, and the like. Requests such as for bedside delivery ofdischarge medications might be formatted as orders or results messagesand sent back to the EMR system 104 for documentation and appropriateaction. Similarly patient feedback, surveys, service recovery can bereported in a variety of formats to messaging systems and/orapplications (like Vocera), or email, text message, and the like.

In step 1206 of method 1200, the integration application program 228operating on the integration server 106 sends the patient requests andfeedback data 214 to the EMR system 104 so that appropriate action canbe taken.

Referring now to FIG. 13, steps for a patient meal ordering data moduleof the present invention is shown and described in accordance withmethod 1300. In step 1302 of method 1300, the executable program 410operating on the smart television 118 sends patient meal orders 216 tothe application server 108 as a result of the user sending requestingsuch meal orders 216 through the user meals menu 508.

In step 1304 of method 1300, the system application program 306operating on the application server 108 sends the patient meal orders216 to a third party food service interface. It will be understood thatsuch web-based food services provide dietary and nutrition services andsystems to a given institution. The display and categorization of mealscan be designed for each user interface 406 for each institution. Inthis embodiment, as the patient navigates the user interface 406, mealsspecific to the patient's diet are dynamically obtained through the userinterface 406 and rules and restrictions are computed before the patientmakes the final selection that is then passed back to the appropriatedietary and nutrition services and systems.

Referring now to FIG. 14, steps for a patient HVAC control module of thepresent invention is shown and described in accordance with method 1400.In step 1402 of method 1400, the executable program 410 operating on thesmart television 118 sends patient HVAC control requests 218 to theapplication server 108 as a result of the user sending such HVAC controlrequests 218 (e.g., increase room temperature) through the stay menuitem 510.

In step 1404 of method 1400, the system application program 306operating on the application server 108 sends the patient HVAC controlrequests 218 data to the institution HVAC system. It will be understoodthat the integration server 106 communicates with the application server108 when ADT data 202 messages are received to request room temperaturesbe set to default values.

Referring now to FIG. 15, steps for a patient bedside monitoring moduleof the present invention is shown and described in accordance withmethod 1500. In step 1502 of method 1500, the system application program306 operating on the application server 108 receives a request forbedside monitoring from a third party video conferencing system.

In step 1504 of method 1500, the system application program 306operating on the application server 108 sends a notification to the userinterface 406 of the smart television 118 to switch the smarttelevision's 118 input to the appropriate source to receive the videoconference. It will be understood that the user consent for this step isnot required, and a device may be “hijacked” such that the healthcareprofessional can view the patient in a videoconferencing setting at anytime the healthcare professional deems such a virtual visit iswarranted. It will be further understood that additional componentsattached to the smart television 118 is configured to allow two-wayaudio and video communication between healthcare professional, patient,and patient guardians where applicable, through its various hardware andsoftware features as shown and described herein.

In step 1506 of method 1500, the executable program 410 operating on thesmart television 118 enables the videoconferencing to commence on thedisplay 408 of the smart television 118.

In step 1508 of method 1500, the system application program 306operating on the application server 108 sends a notification to thesmart television 118 that the videoconference session has concluded.

In step 1510 of method 1500, the executable program 410 operating on thesmart television 118 displays the original user interface 406 on thesmart television 118.

Referring now to FIG. 16, steps for a patient entertainment module ofthe present invention is shown and described in accordance with method1600. In step 1602 of method 1600, the executable program 410 operatingon the smart television 118 displays the entertainment data 226 on theuser interface 408 located on the display 408 of the smart television118.

In step 1604 of method 1600, the system application program 306operating on the application server 108 accesses system entertainmentdata 320 stored in the database server 110 per the patient's selection.

In step 1606 of method 1600, the system application program 306operating on the application server 108 sends system entertainment data226, stored in the system database 110, to the smart television 118.

In step 1608 of method 1600, the system application program 306operating on the application server 108 utilized the streaming server114 to allow for the seamless viewing of video entertainment data 226 onthe user interface 408 located on the display 408 of the smarttelevision 118.

It will be understood that although new data in the institution's EMRsystem 104 and elsewhere is updated across the relevant components ofthe system 100 databases as such new data is received, the typicalprocess for displaying the updated information is to refresh such dataon the specific screens of the user interface 406 that the patient isaccessing.

Referring now to FIG. 17, an embodiment of an interactive sharing ofpatient-related information method 1700 is shown. It will be understoodthat, in this embodiment, the method is described from the perspectiveof the user of the system 100.

In step 1702 of method 1700, the user accesses the system 100 through asmart television 118 located in a patient room.

In step 1704 of method 1700, the user requests patient medication data204 from a menu item located on the user interface 406 displayed on thesmart television 118.

In step 1706 of method 1700, the user views the requested patientmedication data 204 on the display 408 of the smart television 118.

In step 1708 of method 1700, the user requests nursing assessment data206 from a menu item located on the user interface 406 displayed on thesmart television 118.

In step 1710 of method 1700, the user views the requested nursingassessment data 206 on the display 408 of the smart television 118.

In step 1712 of method 1700, the user requests orders and results data208 from a menu item located on the user interface 406 displayed on thesmart television 118.

In step 1714 of method 1700, the user views the requested orders andresults data 208 on the display 408 of the smart television 118.

In step 1716 of method 1700, the user requests diet orders data 210 froma menu item located on the user interface 406 displayed on the smarttelevision 118.

In step 1718 of method 1700, the user views the requested diet ordersdata 210 on the display 408 of the smart television 118.

In step 1720 of method 1700, the user requests patient education data212 from a menu item located on the user interface 406 displayed on thesmart television 118.

In step 1722 of method 1700, the user views the requested patienteducation data 212 on the display 408 of the smart television 118.

In step 1724 of method 1700, the user provides feedback relating to therequested patient education data 212 through user input menu itemslocated on the user interface 406 on the display 408 of the smarttelevision 118.

In step 1726 of method 1700, the user sends requests and feedback data214 through selection of a menu item located on the user interface 406displayed on the smart television 118.

In step 1728 of method 1700, the user sends meal orders 216 throughselection of a menu item located on the user interface 406 displayed onthe smart television 118.

In step 1730 of method 1700, the user sends HVAC control requests 218through selection of a menu item located on the user interface 406displayed on the smart television 118.

In step 1732 of method 1700, the user receives physician bedsidemonitoring visits through the display 408 of the smart television 118.

In step 1734 of method 1700, the user selects entertainment data 226through selection of a menu item located on the user interface 406displayed on the smart television 118.

In step 1736 of method 1700, the user views the requested entertainmentdata 226 on the display 408 of the smart television 118.

It will be understood that not all of the steps in the methods describedherein are required, or must be performed in the order as describedherein.

Referring now to FIG. 18, an embodiment of a command-and-control system1800 for the control of a media and communications system is shown.

The command-and-control system 1800 includes one or more types of userdevices such as a mobile phone or tablet that performs any of thefunctions of a computer, typically having a touchscreen interfacedesigned to be controlled through haptic contact engagement and anoperating system capable of running downloaded applications, here shownas a smartphone device 1802 and a tablet device 1804.

The command-and-control system 1800 also includes other componentsincluding a wireless local area networking system 1808, a facilityapplication control server 1810, a facility local area network 1812, auser display terminal such as a flat-screen television 1814 or otherendpoint device, a mobile application server 1820, and a cloud server1816. It will be understood that the system 1800 may include othercomponents as necessary for the proper functioning of the system 1800.

Referring now to FIG. 19A, another aspect of the command-and-controlsystem 1800 is shown. Here, the command-and-control system 1800 utilizesuser devices 1802 and 1804, which are configured to allow end users (forexample, clinicians, patients, and patient family members) to interactwith and otherwise utilize the command-and-control system 1800. It willbe understood that any number of other devices, in addition tosmartphone device 1802 and tablet device 1804 can be utilized by thesystem, and that smartphone device 1802 and tablet device 1804 are beingoffered as examples herein.

In this embodiment, each device utilizes an executable mobileapplication program 1806, which is stored on each device 1802 and 1804.The mobile application program 1806 is downloaded onto each device 1802and 1804 from a mobile application server 1820 (cloud-based or local),and each device 1802 and 1804 is periodically updated through real timeInternet communications between the mobile application server 1820 andeach device such as smartphone device 1802 and tablet device 1804.

The mobile application program 1806 includes one or more executableprogram files containing instructions to perform various operationsallowing the user devices to properly interact with the system as shownand described herein. For example, when operating on each user devicesuch as smartphone device 1802 and tablet device 1804, the mobileapplication program 1806 causes each user device to provide a userinterface 1902 to each user, and, through the hardware and softwareconfigurations of such user devices 1802 and 1804, allow each user tocontrol each user device through haptic contact engagement on thescreens 1904 of each such device.

The mobile application program 1806 is also configured to communicatewith the facility application control server 1810 over a wireless localarea networking system 1808 such as WiFi (in accordance with standard802.11 of the Institute of Electrical & Electronics Engineers (IEEE), asamended from time to time) to send and receive control commands 1826 andinformation, and to pair with the television 1814 or other end pointdevice that is being controlled by the user.

The facility application program 1818 operating on the facilityapplication server includes one or more executable program filescontaining instructions to perform various operations to operate thefacility application. The facility application 1818 can be any number ofapplications including the systems and methods described in U.S.Provisional Application No. 62/420,945, or other facility, home orbusiness media and communications systems.

The facility application program 1818 is configured to receive controlcommands 1826 and information from the mobile application programs 1806operating on the user devices, such as smartphone device 1802 and tabletdevice 1804, and send commands 1828 directly to the endpoint device1814.

The endpoint device 1814 has an endpoint device application program 1824that includes one or more executable program files containinginstructions to perform various operations to control the endpointdevice 1814 and communicate with the facility application program 1818.The endpoint device application program 1824 is configured to receivecommands 1828 from the facility application 1818 and control the contentand navigation of what appears on the endpoint device 1814 display 1822.It will be understood that the endpoint device application program 1824can be stored on an endpoint device control box 1830, or in anotherstorage and control device or location, rather than on componentslocated on or within the endpoint device 1814 itself.

It will be further understood that each of the command-and-controlsystem 1800 components contains non-transient computer readable storagemediums, or other storage mediums, on which such components are capableof storing information including executable and non-executable computercode, related source code, course code, binary files, applicationprogram interfaces (APIs), and/or other executable code or instructions.It will be further understood that communication between any or all ofthe command-and-control system 1800 components can be performed throughoperation of one or more application program interfaces (APIs) locatedon or accessible through any of the system 1800 components, including inconjunction with any application programs stored or otherwise utilizedby the system 1800.

Referring now to FIG. 19B, further details of the components of asmartphone device 1802 or tablet device 1804 are shown. In thisembodiment, smartphone device 1802 and/or tablet device 1804 includes anumber of components including, but not limited to, a display 1902, anexecutable program 1904, processor 1906, power supply (battery orhardwire) 1908, storage memory component 1910, camera (with two-wayvideo and audio capability) 1912, and camera/video controller 1914,wireless processor 1916, touch sensors 1918, touch controller 1920,audio receiver 1922, and audio speaker 1924. It will be understood thatthese are examples of components utilized with the command-and-controlsystem 1800, but it will be further understood that the smartphone 1802or tablet 1804 devices can include any number of other components thatcan be utilized by the command-and-control system 1800 in accordancewith the manners described herein and otherwise.

Referring now to FIG. 20, further aspects of devices 1802 and 1804 areshown, here using tablet device 1804 to illustrate various controlfeatures. Tablet device 1802 has a display 2002, and the mobileapplication program 1806 operating on tablet device 1804 containsexecutable instructions to display a graphical user interface 2004 onthe display 2002. The graphics and command icons displayed on thedisplay 2002 can vary in terms of visual features and organizations,depending on how the mobile application program 1806 is programmed. Suchdisplay can be in menu format (with drop down options), icon format(with icons arranged in various ways on the display of the smartphonedevice 1802), or a combination of both.

In this embodiment, the graphical user interface 2004 provides variouscontrol icons 2001 visually displayed as icons on the interface 2004.Such control icons 2001 are provided to control the navigation among,and content of, what is being displayed on a television 1814 or otherend point device screen 1822. Such control icons 2001 include, but arenot limited to, an on/off control 2006 configured to control turning theendpoint device application program 1824 and/or endpoint device 1814 onor off; a search control 2008 configured to control the searchfunction/magnifying glass where the user is allowed to type in words orletters and navigate more quickly within a particular screen or pagehaving certain content, such as within an education library, moviecategory, or medication list shown on the endpoint device 1814 display1822; a keyboard control 2010 configured to provide letters, numbers,page up/down, caps lock/shift, backspace/delete, enter, calculator,allowing the user to enter and send data to the facility applicationserver 1810 through the facility application program 1818; a downloadcontrol 2012 configured to provide a button (such as an arrow) that whenclicked on (through haptic engagement) allows a user to download thatparticular information asset (such as a handout, pdf, video, or otherinformation) from the application server 1810 or other server within thefacility system; a mousepad control 2014 configured to allow haptictouch-application manipulation of the cursor on the screen, like a mousewould on a computer; and a swipe left/right control 2016 configured toallow the user to swipe to move from application to application beingdisplayed, for example, on the endpoint device 1814, or quicklyadvance/scroll right/left through a number of information assets in acollection such as movies, education data, or other items.

Such control icons 2001 also include a scrolling up/down control 2018configured to allow the user to quickly advance/scroll up/down through anumber of information assets in a collection such as education titles ordietary items; a page up/down control 2020 configured to allow the userto quickly advance/scroll up/down (as above) through pages ofinformation assets; a channel up/down control 2022 configured to allowthe user to navigate the controls of the television 1814 or other endpoint device; an up/down, right/left and select arrows control 2024configured to allow the user to incrementally move the focus ofnavigation and control 1 space up/down/left/right and choose it with the“select” button; an information button control 2026 configured toprovide a button/icon such as a circled “I” that, when clicked on, wouldexpand with more information, allowing the access and viewing ofinformation on medications, dietary, movies, education, and other items,including program descriptions displayed on the smartphone device 1802interface 2004 while viewing the content on the television 1814 or otherend point device; and an information icon control 2028 which isconfigured to resemble the information button control 2026 but which isdisplayed on the television 1814 or other end point device screen 1822(discretely at the bottom/side of the screen 1822) allowing, as withinformation button control 2026, the access and viewing of informationon medications, dietary, movies, education, and other items, includingprogram descriptions while viewing the content on the television 1814 orother end point device.

Such control icons 2001 also include a movie viewing control 2030configured to provide commands/trick modes (e.g., Fast Forward, Rewind,Play/Pause, Stop, Save); a closed captioning control 2032 configured toprovide several closed captioning options, toggling or turning on/offwith the same button; a guide control 2034 configured to allow the userto go directly to the Electronic Programming Guide and displayinformation about the television shows; a number keys control 2036configured to provide channels, amounts (like in food ordering), andrelated items; a pointer control 2038 configured to allow the user todirectly access certain area in the application or TV (banners,Information button, and related items; and a quick buttons control 2040configured to provide users with access to popular features such asmovies, dining, or home page.

Such control icons 2001 also include an exit control 2042 configured toallow the user to exit the application, movie, or other like applicationor content; a mute button control configured to allow the user to mutesound; a last control 2044 configured to allow the user to go directlyto the last channel or could display list or graphics along bottom ofscreen showing “trail” of last viewed channels or applications; afavorites control 2046 configured to allow the user to manually accessfavorite channels/apps as entered by user or determined by most views; ahome button control 2048 that allows the user to navigate to the homepage of the respective application; an internet button control 2050configured to allow the user to navigate to Internet (URL of choice); asettings control 2052 configured to allow the user to change deviceinputs, customize look of the application; and a data entry control 2054configured to present a data entry box and keyboard to allow the user toput input notes or access a website.

It will be understood that the icons on the user interface 2004 caninclude all or a portion of the controls shown on the display of theendpoint device 1814. Thus, what is shown on the user interface 2004 ishighly customizable based on the needs and desires of the institution ororganization utilizing the system 1800. It will be understood that whatis in fact displayed to the user on the user interface 2004,particularly in terms of control icons, is determined by the deviceapplication programs 1806 operating on each user device, in coordinationwith the facility application program 1818.

It will be further understood that the system 1800 is also configured toallow a user to navigate with his or her mobile device of choice (e.g.,a smartphone device 1802, tablet device 1804, wearable, or other relateditems) in conjunction with, if desired, the traditional remote/pillowspeaker, based on the needs of the user and/or institution. Thus,navigation could simultaneously be controlled with one paired device,e.g. smartphone device 1802, along with multiple unpaired devices, suchas a pillow speaker or wireless remote.

It will be further understood that the system 1800 could also beconfigured to connect with Adaptive Devices such as sip/puff controls(that is, when a user sips on a straw or exhales into a tube as a way toprovide commands into the system 1800); modularize certain componentsthrough a single button that brings up trick modes; and provide a“simplified” version with less features/functions to those who need lesscomplex navigation, like Adaptive Devices such as sip/puff. For example,users with certain neurological handicaps (e.g. stroke or Parkinson'sdisease) may also use assistive technology to actuate the system.

It will be further understood that the system 1800 could also beconfigured to provide a Customer Relationship Management (CRM) componentthat would help clients use, manage and analyze (in a hospital setting)patient data throughout their relationship (inpatient and outpatient).An example use case is the ability to push previously stored patientpreferences (e.g. entertainment, education, adaptive UI, language,“favorites”-either by frequency of user behavior or pre-defined by user)and adjust the user interface (UI). Another use case is recording andsending/storing patient device information (Operating System, phonenumber, email, credentials and related items) to hospital forfollow-up/post discharge contact. It will be understood that collectingthe above data can be a function of the endpoint device application, themobile application program 1806, or integrated combination of both.

It will be further understood that the system 1800 could also beconfigured to store and report on user activity (button clicks, quickbuttons and related items) for continuous quality improvement of theapplication; run multiple applications in parallel (such as email, text,and the Internet), running on personal devices having button/icon foreasy access; and have the ability to have more than one device controlthe television 1814 or other end point device or facility applicationprogram 1818, including the ability to allow a family member of a user(such as a patient in a healthcare facility) to navigate with his or herown device should the originally paired device lose battery charge orotherwise become inoperative because of malfunction, choice, orotherwise.

It will be further understood that the system 1800 could also beconfigured to allow users to personalize the user interface of eachdevice in color or layout styles; “wipe”/purge data when leaving theinstitution (such as in a hospital/health care system environment);allow for voice commands and/or voice recognition to navigate and turnon/off, such as through a microphone button; provide the ability to becontrolled in multiple languages, including voice recognition in user'schosen language; and allow for user devices to display a prompt to synctheir device with the television 1814 or other end point device whenwithin a predefined distance from the television 1814 or other end pointdevice.

It will be understood that the above-references features and controlsare by way of example only, and the user interface can include otherfeatures and controls. It will be further understood that the pillowspeaker controls, other remote controls, or controls including voicecontrol or sip/puff can perform such functions or other functions inparallel with the systems and methods described herein.

It will be further understood that the mobile application program 1806can be configured to display any number of other controls 2006 tocontrol or otherwise interact with the facility application program 1818operating on the facility application server 1810. It will be furtherunderstood that the mobile application program 1806 is configured tosend and receive information and media content, such as text messages,video content, audio content, real-time communications, and othercontent.

The facility application program 1818 operating on the facilityapplication server 1810 is configured to receive commands from themobile application program 1806, analyze the information, and sendinstruction to the appropriate end-point device (in this case a flatscreen television 1814 or other end point device) for the room and bedassociated with a patient. The application 1824 running on the end-pointdevice 1814 is configured to receive the information from the facilityapplication program 1818 and perform the navigation desired, display theappropriate screen/feature, store/modify information stored for thatpatient (e.g. add personal notes for themselves), or perform the desiredfunction.

Referring now to FIG. 21, a method 2100 for controlling a media andcommunications system is shown.

In step 2102 of method 2100, a user downloads onto a smartphone device1802 a mobile application program 1806 from a mobile application server1820 over the Internet and/or a wireless local area networking system1808.

In step 2104 of method 2100, the mobile application program 1806operating on the smartphone device 1802 communicates over a securedwireless local area networking system 1808 with the facility applicationserver 1810. Such secured protocols may include WEP, WPA, WPA2 or othersecurity that the organization may have implemented.

In step 2106 of method 2100, the user information is authenticated. Forexample, in a hospital setting, the information provided in this stepcould be the name of the patient along with visit/account number ormedical record number.

In step 2108 of method 2100, the smartphone device 1802 is paired withthe television 1814 or other end point device. For example, in ahospital setting, the information provided in this step is the roomnumber. This step 2104 could be done via a QR scan on the TV in thepatient room.

In step 2110 of method 2100, once authentication is complete, theappropriate control icons 2001 are displayed on the interface 2014, asdetermined by the mobile application program 1806 and facilityapplication program 1818 on what controls will populate the display2004. At this stage the user is able to start controlling the television1814 or other end point device via the control icons 2001 or otherwise.

In step 2112 of method 2100, commands from the mobile applicationprogram 1806 are sent to the facility application program 1818 via APIs.These commands can be activated as a result various functions, includingthose described herein, such as through haptic contact engagement withthe command icons 2001 through 2052, sip/puff, voice control, and/orother activations.

In step 2114 of method 2100, the command information received by thefacility application program 1818 is processed by the facilityapplication program 1818 and sent to the television 1814 or other endpoint device for appropriate action via APIs, resulting in user controlover the television 1814 or other end point device

In step 2116 of method 2100, if the information received from the mobileapplication program 1806 is not directly related to display on thetelevision 1814 or other end point device, the facility applicationprogram 1818 might directly act on the data submitted to appropriatelystore/modify information stored for that patient (e.g. add personalnotes for themselves) or trigger the activity desired by the specificcommand via other sets of APIs or interfaces (e.g. change roomtemperature).

It will be understood that not all of the steps in the methods describedherein are required, or must be performed in the order as describedherein.

The embodiments of the invention described above are intended to bemerely exemplary; numerous variations and modifications will be apparentto those skilled in the art. All such variations and modifications areintended to be within the scope of the present invention as defined inany appended claims.

What is claimed is:
 1. A patient-related information delivery system fordelivering patient-related information to a patient located in ahospital room, the patient-related information delivery systemcomprising: one or more virtual machine servers, wherein the one or morevirtual machine servers are configured to be communicatively coupled toan electronic medical records database and one or more in-room devices,wherein the one or more in-room devices are configured to be utilized bythe patient located in the hospital room; and one or more processorscoupled to the one or more virtual machine servers, wherein the one ormore processors are configured to: cause the one or more virtual machineservers to receive patient data from the electronic medical recordsdatabase that relate to one or more patients; cause the one or morevirtual machine servers to parse the patient data into a format usableby the one or more virtual machine servers, thereby creating parsedpatient data; cause the one or more virtual machine servers to store theparsed patient data; cause the one or more virtual machine servers toenable the one or more in-room devices in the hospital room to receiveand display the patient-related information; cause the one or morevirtual machine servers to match the patient located in the hospitalroom to one of the one or more in-room devices; and cause the one ormore virtual machine servers to send a command to the one of the one ormore in-room devices to display the patient-related information; thepatient-related information delivery system further comprising a userdevice comprising a processor, wherein the processor of the user deviceis configured to: retrieve an application for the user device, whereinthe application is configured to communicate with a facility applicationserver; communicate user information, via the application, to thefacility application server so that the facility application server canauthenticate the user device, wherein the communication occurs over asecure connection; pair the user device with the endpoint device; uponauthentication, display control icons on a display of the user device;and send one or more commands from the user device to the facilityapplication server so that the facility application server can forwardthe one or more commands to the endpoint device to cause the endpointdevice to perform an action based on the one or more commands.
 2. Apatient-related information delivery method for deliveringpatient-related information to a patient located in a hospital room, thepatient-related information delivery method comprising: receiving, byone or more virtual machine servers, patient data from an electronicmedical records database that relate to one or more patients; parsing,by the one or more virtual machine servers, the patient data into aformat usable by the one or more virtual machine servers, therebycreating parsed patient data; storing, by the one or more virtualmachine servers, the parsed patient data; enabling, by the one or morevirtual machine servers, one or more in-room devices in the hospitalroom to receive and display the patient-related information; matching,by the one or more virtual machine servers, the patient located in thehospital room to one of the one or more in-room devices; sending, by theone or more virtual machine servers, a command to the one of the one ormore in-room devices to display the patient-related information;retrieving, by a user device, an application for the user device,wherein the application is configured to communicate with a facilityapplication server; communicating, by the user device, user information,via the application, to the facility application server so that thefacility application server can authenticate the user device, whereinthe communication occurs over a secure connection; pairing, by the userdevice, the user device with the endpoint device; upon authentication,displaying, by the user device, control icons on a display of the userdevice; and sending, by the user device, one or more commands from theuser device to the facility application server so that the facilityapplication server can forward the one or more commands to the endpointdevice to cause the endpoint device to perform an action based on theone or more commands.